You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The solution is to just export the Store type, allowing the type "to be named".
I think it's useful anyhow, since users who use createStore might need to describe it as a type as well.
A wider solution would be to not use the export ... from '...' syntax, it seems that it's the primary case of this specific error across different packages.
--
Thank you!
Loves this library
The text was updated successfully, but these errors were encountered:
Hi
I've noticed a type issue when using
createStorein a TS environment.Whenever it's used, the following error appears:
TS config
I think it can be fixed by tweeking the
module&moduleResolution, but that's not possible for every project.In my case it's:
{ "compilerOptions": { "useDefineForClassFields": true, "lib": ["ES2020", "DOM", "DOM.Iterable"], "skipLibCheck": true, "moduleResolution": "bundler", "resolveJsonModule": true, "isolatedModules": true, "allowSyntheticDefaultImports": true, "forceConsistentCasingInFileNames": true, "noUnusedLocals": true, "noUnusedParameters": true, "strictNullChecks": true, "jsx": "react-jsx", "strict": true, } }Solution
The solution is to just export the
Storetype, allowing the type "to be named".I think it's useful anyhow, since users who use
createStoremight need to describe it as a type as well.A wider solution would be to not use the
export ... from '...'syntax, it seems that it's the primary case of this specific error across different packages.--
Thank you!
Loves this library
The text was updated successfully, but these errors were encountered: